To view the most up-to-date version of the Visual Studio 2008 Express Editions Readme, click here.
Table of Contents
1.2. Supported Operating Systems
Upgrading from the CTP and Beta versions of SQL Server Compact 3.5 to the release version is not supported.
To resolve this issue:
Before you install the release version of either SQL Server Compact 3.5 or Visual Studio 2008, uninstall all CTP and Beta versions of SQL Server Compact 3.5, SQL Server Compact 3.5 for Devices, and SQL Server Compact 3.5 Design Tools.
Users get the error message, "A problem has been encountered while loading the setup components. Canceling setup" and then Setup is cancelled. This only occurs on systems that do not have Windows Installer 3.1. Users should install Windows Installer 3.1 and then retry Setup.
To resolve this issue:
1. In Add or Remove Programs (or Programs and Features, for Windows Vista), look for Windows Installer 3.1 in the list of installed programs.
2. If Windows Installer 3.1 is not present, complete the following steps.
a. Go to Windows Installer 3.1 Redistributable (v2) and then install Windows Installer 3.1.
b. Retry Visual Studio 2008 Setup.
Setup stops and displays an error message, "Setup failed to stop Windows Installer service. You must stop all other applications running Windows Installer service or restart your computer before the installation".
To resolve this issue:
Try the following options:
- This message indicates that a setup program other than Visual Studio 2008 Setup might already be running on the computer. After the other setup is finished, restart the computer and then run Visual Studio 2008 Setup.
- This message might also indicate that Windows updates are being installed on the computer. After Windows Update is finished, restart the computer and then run Visual Studio 2008 Setup.
- Look for msiexec.exe in Task Manager. If msiexec.exe is already running, wait for it to finish and then restart the computer and run Visual Studio 2008 Setup.
- If none of these options apply to your problem, restart your computer and then run Visual Studio 2008 Setup.
When Visual Studio 2008 is installed on the same computer as Visual Studio 2005, Visual Studio 2005 repair fails to repair the .NET Framework 2.0.
To resolve this issue:
Repair .NET Framework 2.0 separately by using Add or Remove Programs (or Programs and Features, for Windows Vista).
Visual Studio 2008 Setup may display a message that prompts you to close running applications. In the message, some of the applications may have a numeric process identifier and some may have an empty identifier. Names of applications are not shown.
To resolve this issue:
We recommend that you close the applications so that they do not affect the installation process.
You can find the names of the applications by looking up their Process IDs in Task Manager.
1. Press CTRL+ALT+DEL and then click Task Manager.
2. On the View menu, click Select Columns.
3. Select PID (Process Identifier) and then click OK.
4. In Task Manager, click PID to sort entries by PID.
5. Look for the Process IDs that are shown in the message.
You may also click Ignore in the message box and then continue with the installation. Doing this may require a reboot at the end of Setup.
- User choses to repair Visual studio express language pack from Add or Remove Programs (or Programs and Features, for Windows Vista).
- When the dialog appears to select whether to locate the source media or to download it again, user select the source media.
- User is not able to select SFX that contains the media because source media option is to select CD layout.
To resolve this issue:
Option 1:
- Repair Visual studio express language pack from Add or Remove Programs (or Programs and Features, for Windows Vista).
- When the dialog appears to select whether to locate the source media or to download it again, select option to download.
Option 2:
Uncompress SFX and select in source media option
Visual Studio 2008 uninstallation may display a message that prompts you to close running applications. In the message, some of the applications may have a numeric process identifier and some may have an empty identifier. Names of applications are not shown.
To resolve this issue:
We recommend that you close the applications so that they do not affect the installation process.
You can find the names of the applications by looking up their Process IDs in Task Manager.
1. Press CTRL+ALT+DEL and then click Task Manager.
2. On the View menu, click Select Columns.
3. Select PID (Process Identifier) and then click OK.
4. In Task Manager, click PID to sort entries by PID.
5. Look for the Process IDs that are shown in the message.
You may also click Ignore in the message box and then continue with the uninstallation. Doing this may require a reboot at the end of uninstallation.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
Visual Studio Express uninstallation may display a message that prompts you to close running applications. In the message, some of the applications may have a numeric process identifier and some may have an empty identifier. Names of applications are not shown.
To resolve this issue:
We recommend that you close the applications so that they do not affect the installation process.
You can find the names of the applications by looking up their Process IDs in Task Manager.
1. Press CTRL+ALT+DEL and then click Task Manager.
2. On the View menu, click Select Columns.
3. Select PID (Process Identifier) and then click OK.
4. In Task Manager, click PID to sort entries by PID.
5. Look for the Process IDs that are shown in the message.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
In Visual Studio 2008 Beta 2, the O/R Designer created .dbml files as UTF-8 byte-order even if UTF-16 encoding was specified in the actual file. Opening .dbml files created by using Beta 2 could raise the "There is no Unicode byte order mark. Cannot switch to Unicode" error.
To resolve this issue:
Right-click the .dbml file in Solution Explorer, open by using the XML Editor, and then save the file. Doing this does not impact the actual content of the .dbml file and there is no data loss.
ClickOnce applications cannot be published to a remote server by using FTP or HTTP from Visual Basic Express or C# Express.
When you try to publish a ClickOnce application to a remote server by using FTP or HTTP from Visual Basic Express or C# Express, you receive the message, "Failed to connect to '<server_name>' with the following error: Unable to create the Web site '<server_name>'. The components for communicating with FrontPage Server Extensions are not installed."
To resolve this issue:
1. Install Visual Web Developer Express Edition, or use a local file path to publish, that is, '\publish'.
2. Use Windows FTP or an external FTP program to copy the entire '\publish' directory to your remote server.
For more details on this issue check here: http://go.microsoft.com/fwlink/?LinkId=102310
The Encrypt property in the SqlCeConnection class should not be used. The property is retained in SQL Server Compact 3.5 only for backward compatibility.
To resolve this issue:
Use the encryption mode property of the SqlCeConnection class to encrypt SQL Server Compact 3.5 database files. Uses of encryption mode, together with code samples, are as follows.
1. To create a new encrypted SQL Server Compact 3.5 database.
[Visual C#]
SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;encryption mode=platform default;Password=password#1;"); engine.CreateDatabase();
[Visual Basic]
Dim engine As SqlCeEngine engine = New SqlCeEngine("Data Source=Northwind.sdf;encryption mode=platform default;Password= password#1;") engine.CreateDatabase()
2. To upgrade a SQL Server 2005 Compact Edition (version 3.1) or SQL Server 2005 Mobile Edition (version 3.0) database to an encrypted SQL Server Compact 3.5 database.
[Visual C#]
SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password= password#1;"); engine.Upgrade ("Data Source=Northwind.sdf;encryption mode=platform default;Password= password#2;");
[Visual Basic]
Dim engine As SqlCeEngine engine = New SqlCeEngine("Data Source=Northwind.sdf;Password=password#1;") engine.Upgrade("Data Source=Northwind.sdf;encryption mode=platform default;Password=password#2;")
3. To change the encryption mode of an existing SQL Server Compact 3.5 database.
[Visual C#]
SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password= password#1;"); engine.Compact("Data Source=Northwind.sdf;encryption mode=ppc2003 compatibility;Password= password#1;");
[Visual Basic]
Dim engine As SqlCeEngine engine = New SqlCeEngine("Data Source=Northwind.sdf;Password=password#1;") engine.Compact("Data Source=Northwind.sdf;encryption mode=ppc2003 compatibility;Password=password#1;")
4. To encrypt an unencrypted SQL Server Compact 3.5 database.
[Visual C#]
SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf"); engine.Compact("Data Source=Northwind.sdf;encryption mode=platform default;Password= password#1;");
[Visual Basic]
Dim engine As SqlCeEngine engine = New SqlCeEngine("Data Source=Northwind.sdf;") engine.Compact("Data Source=Northwind.sdf;encryption mode=platform default;Password=password#1;")
Database files (*.sdf) that are created by earlier version of SQL Server Compact are not compatible with SQL Server Compact 3.5. Un-encrypted database files from earlier versions of SQL Server Compact are upgraded when a Visual Studio 2005 project is upgraded in Visual Studio 2008. Encrypted database files must be manually upgraded. If the Visual Studio 2005 project uses ClickOnce to publish applications, the application should be re-published after the project has been upgraded in Visual Studio 2008.
To resolve this issue:
Upgrade the encrypted database files by completing the following steps.
1. Click Data.
2. Click Add New Data Source.
3. Click Add Connection. If an earlier version of the database file is open, a message appears. If you click OK, the Upgrade to SQL Server Compact 3.5 Database dialog box appears.
Alternatively the SqlCeEngine.Upgrade API can be used for programmatic scenarios, as shown in the following code example.
[Visual C#]
SqlCeEngine engine = new SqlCeEngine("Data Source=Northwind.sdf;Password=passw0rd;");
engine.Upgrade ("Data Source=Northwind.sdf;encryption mode=platform default;Password=passw0rd;");
[Visual Basic]
Dim engine As SqlCeEngineIf the project uses ClickOnce to publish applications, the application should be re-published after it has been upgraded in Visual Studio 2008. When you re-publish the Click Once application in Visual Studio 2008, you may see a warning that SQL Server 2005 Compact Edition prerequisite cannot be found for bootstrapping. You can ignore the warning.
If the data types for parameters such as SqlDbType or DbType are not explicitly set, an exception will be thrown.
To resolve this issue:
Explicitly set the data type for parameters such as SqlDbType or DbType. Doing this is critical in case of BLOB data types (image and ntext). A code example follows.
[Visual C#]
SqlCeEngine engine = new SqlCeEngine(connString);
engine.CreateDatabase();
engine.Dispose();
SqlCeConnection conn = new SqlCeConnection(connString);
conn.Open();
SqlCeCommand cmd = conn.CreateCommand();
cmd.CommandText = "CREATE TABLE BlobTable(name nvarchar(128), blob ntext);";
cmd.ExecuteNonQuery();
cmd.CommandText = "INSERT INTO BlobTable(name, blob) VALUES (@name, @blob);";
SqlCeParameter paramName = cmd.Parameters.Add("name", SqlDbType.NVarChar, 128);
SqlCeParameter paramBlob = cmd.Parameters.Add("blob", SqlDbType.NText);
paramName.Value = "Name1";
paramBlob.Value = "Name1".PadLeft(4001);
cmd.ExecuteNonQuery();
[Visual Basic]
Dim engine As SqlCeEngineThere are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
3.1. Visual Studio Readme: http://go.microsoft.com/fwlink/?LinkId=102508
3.2. .NET Framework Readme:http://go.microsoft.com/fwlink/?LinkId=1102511
3.3. MSDN Library for Visual Studio Readme: http://go.microsoft.com/fwlink/?LinkId=102512
3.4. Download SQL Server Compact 3.5 Books Online and Samples from http://go.microsoft.com/fwlink/?LinkID=96191 and Synchronization Services for ADO.NET v1.0 Books Online and Samples from http://go.microsoft.com/fwlink/?LinkId=80742. To add these to the Visual Studio Combined Help Collection, complete the following steps.
1. Click Start, point to All Programs, Microsoft Visual Studio
2008, and then click Microsoft Visual Studio 2008 Documentation.
2. In the Visual Studio Combined Help Collection, click Help and then click Index.
3. In the Look for box, enter collection manager, and then
click the Help entry under collection manager in the Index.
4. In the Combined Help Collection Manager topic, select SQL
Server Compact 3.5, and then click Update VSCC.
5. In the two dialog boxes that appear, read the requirements,
and then click OK.
6. Close and then reopen the Visual Studio Combined Help Collection.
SQL Server Compact Books Online is now available in the Table of Contents, Index,
Search, and F1 Help.
3.5. For the latest information about issues with using the WPF designer in Visual Studio 2008, see the Cider wiki on Channel9, http://go.microsoft.com/fwlink/?LinkId=83541.
3.6. Visual J# MSDN developer center:http://go.microsoft.com/fwlink/?LinkId=102513
3.7. The XML to Schema tool can be downloaded from http://go.microsoft.com/fwlink/?LinkId=102514
The XML to Schema tool is a free project-item template that automates the creation
of XML schema sets from any number of XML documents. If you are working with LINQ
to XML in Visual Basic 2008, this utility may significantly improve your editing
experience by adding XML schemas (.xsd files) to your project that then provide
IntelliSense for XML properties. The tool can also be used to create an XML schema
set from a set of existing XML documents.
© 2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement